|
|
Date: 2001-07-13 14:35:09
When using XML, a big question is : What DTD
or XMLSchema am I going to use in my application ?
You have at least 2 possibilities.
1. |
Use an existing standard
or de Facto DTD. You will find some if you go some of the DTD Repositories (see
also
HREF="http://www.xml.com/pub/rg/DTD_Repositories">http://www.xml.com/pub/rg/DTD_Repositories).
|
HREF="http://www.biztalk.org">Biztalk |
HREF="http://www.dtd.com/">DTD.com |
HREF="http://www.finxml.org/">FinXML |
HREF="http://www.oasis-open.org/html/rrpublic.htm">OASIS |
HREF="http://www.rosettanet.org">RosettaNet |
HREF="http://www.schema.net">schema.net |
HREF="http://www.xml.org">xml.org |
2. |
Design yourself your own DTD. Some
people are now testing methods to deduce a Schema from your actual software
analysis. Some of these methodologies use UML. For example, using UML, XMI and
XSL, you can think of generating Schemas from your Object Oriented Analysis and
Design (OOAD). Here is a very good example of that :
Modeling the UDDI Schema with
UML |
|
Pro and Cons
|
Standard Schema |
Own Schema |
+ |
- The Schema is potentially very well
engineered
- Direct communication with people who have adopted this schema
(WML for WAP is a good example) |
- The Schema will be adapted to your
own need and not to the need of another company or consortium. You can adapt it
to fit your IT capabilities that are suited for your own business needs.
-
Independance to standard changes (versions,...) through XSLT technology. |
- |
The Schema can be difficult to
implement in your IT because it suffers of over-engineering (to complex
structures for your databases, recursive nested definitions, too many entities
to deal with,...) |
- Transformation will be needed to go
to standards but there is a technology for that : XSLT.
- In-house or
external know-how needed to develop the Schemas. For Example XML
Modeling... |
Hope it helps... |
